Skip to content

Conversation

ronjalh
Copy link
Member

@ronjalh ronjalh commented Nov 10, 2026

What

From the peer feedback (#167): "Illustration for 1.00" says little to a screen reader user, and the descriptions are already good.

There are only two places with a drawing, and both have the description right next to it, so one rule is used:

  • Element page (ElementDiagram.tsx): the text is the description of the element ("Clear hip circle to hstd"), because the drawing is the main content. If an element has no description it falls back to "Drawing of ".
  • Cards of the results list (ResultsTable.tsx): the text is empty (alt=""), because the description is in the card just above the drawing, and repeating it for 20 cards would be noise.

The rule is written in docs/ACCESSIBILITY.md, and there is a short entry in docs/AI_USAGE.md.

Checked

  • Tests: the card test now expects an empty text, the element page test expects the description, and the Elements page test finds the images without the img role (an image with an empty text has none). 427 frontend tests pass; tsc, ESLint and Prettier are clean.
  • The axe, element page and Elements flow end-to-end tests pass (20).
  • Not tested with a screen reader. The peer reviewer suggested using the description everywhere; the empty text is correct only because the description is next to the drawing, and the team can choose the other option.

Closes #173

🤖 Generated with Claude Code

The element page uses the description of the element as the text of the
drawing, and the cards of the results list use an empty text, because the
description is in the card just above the drawing. The rule is written in
docs/ACCESSIBILITY.md.

Closes #173
@ronjalh ronjalh requested a review from a team as a code owner November 10, 2026 19:53
@ronjalh ronjalh self-assigned this Nov 10, 2026
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant